Method and system for formatting data from one software application source into a format compatible for importing into another software application

ABSTRACT

A method and system electronically pull, using an extension of a launched program, accounting data from a launched accounting software application. The pulled data is converted, by the extension, into a format compatible with a second accounting software application. The converted data is written into the launched application associated with the extension. The written data is converted, by another extension, into a format compatible for importing into another accounting software application. The format compatible data is pushed into the second accounting software application by the extension.

PRIORITY INFORMATION

The present application is a divisional application of U.S. patent application Ser. No. 14/530,920, filed on Nov. 3, 2014; said U.S. patent application Ser. No. 14/530,920, filed on Nov. 3, 2014, claims priority, under 35 USC §119(e), from U.S. Provisional Patent Application Ser. No. 61/899,250, filed on Nov. 3, 2013; said U.S. patent application Ser. No. 14/530,920, filed on Nov. 3, 2014, claims priority, under 35 USC §119(e), from U.S. Provisional Patent Application Ser. No. 62/014,481, filed on Jun. 19, 2014. The entire content of U.S. patent application Ser. No. 14/530,920, filed on Nov. 3, 2014, is hereby incorporated by reference.

This application claims priority from U.S. Provisional Patent Application Ser. No. 61/899,250, filed on Nov. 3, 2013. The entire content of U.S. Provisional Patent Application Ser. No. 61/899,250, filed on Nov. 3, 2013, is hereby incorporated by reference.

This application claims priority from U.S. Provisional Patent Application Ser. No. 62/014,481, filed on Jun. 19, 2014. The entire content of U.S. Provisional Patent Application Ser. No. 62/014,481, filed on Jun. 19, 2014, is hereby incorporated by reference.

COPYRIGHT

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights.

BACKGROUND

Many conventional accounting software applications offer features to record accounting transactions, balance a bank statement, invoice customers, pay vendors, payroll, budgeting, financial statements, and many other related tasks. With estimates of 20-25 million small businesses in the U.S., there is always a large demand for other features or tasks not offered by the conventional accounting software applications. Customers may use conventional accounting software applications for certain business applications and other software applications or services for other tasks.

For example, a user may use accounting software application A for accounting and Service B for payroll because the user wants payroll to be secured and off-site.

In another example, a user may use accounting software application A for accounting and software application C for invoicing customers

As a result there is a consistent demand to transfer data to and from the accounting software applications. This data can be grouped into two types: (1) lists—a static list of vendors, customers, accounts that changes relatively seldom; and (2) transactions—daily accounting transactions like paying bills, invoicing customers, etc.

If a user is using accounting software application A and another software application B to run a business, it is likely the user may be required to transfer transactions between the two software packages regularly. Lists may need to be updated, but much less often.

Conventionally, some accounting software applications have provided a method of formatting data in a file for the purpose of importing data (both transactions and lists) into the accounting software application.

Many of these file formats are relatively difficult to use and have not been updated since the software application's initial release. In these cases, since these file formats have been the only methods to import data into the conventional accounting software applications, third party software companies have had to deal with it by providing users with the ability to create the formatted files.

For example, a payroll company may allow its customers to download a formatted file containing payroll transactions for the purpose of importing to a specific accounting software application. The customer's objective is to have all financial transactions in the accounting software application in order to have accurate financial statements.

Banks may allow customers to download banking transactions in a formatted file to import into the accounting software application.

A user may adopt the accounting software application in the middle of the year. The user wishes to have all their lists and transactions from earlier in the year, from their prior software, transferred into the newly chosen accounting software application in order to have a complete year in the newly chosen accounting software application. The user may need to find a way to create a formatted file out of their prior software.

Another issue that arises is when an existing accounting software application is re-vamped such that the formatted files associated with the pre-re-vamped accounting software application are no longer compatible for importing. This can cause a negative impact to existing users who switch over to the new software application but are using applications or services which only produce the old formatted files and do not produce the formatted files compatible for importing.

In a further situation, as illustrated in FIG. 4, a user may adopt a new accounting software application after seven months into the fiscal year and want to combine the financial data from the old software application and the financial data from the new software application into a single file to facilitate the preparation of tax returns, end of year financial statements, etc. The user may need to find a way to create a single formatted file from the two software application sources.

Thus, it is desirable to provide a solution that bridges the production of previous generation formatted files with the new format constraints for import compatibility.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are only for purposes of illustrating various embodiments and are not to be construed as limiting, wherein:

FIG. 1 illustrates a block diagram of a system for formatting data from one software application source into a format compatible for importing into another software application;

FIGS. 2 and 3 illustrate a flowchart showing the conversion of data from one format to another format;

FIG. 4 illustrates an issue when utilizing two different formats;

FIG. 5 illustrates an interactive window on a display screen that incorporate the format conversion functionality into a conventional spreadsheet application;

FIG. 6 illustrates a relationship between data tables and a database;

FIG. 7 illustrates a relationship between original format and new format;

FIG. 8 illustrates an example of a vendor table generated by the conversion process; and

FIG. 9 illustrates the process of transferring the spreadsheet data to a new application.

DETAILED DESCRIPTION

For a general understanding, reference is made to the drawings. In the drawings, like references have been used throughout to designate identical or equivalent elements. It is also noted that the drawings may not have been drawn to scale and that certain regions may have been purposely drawn disproportionately so that the features and concepts could be properly illustrated.

In the following description, accounting software application refers to any software application directed to accounting, payroll processing, bookkeeping, invoice processing, account payable processing, accounts receivable processing, bill payment processing, timekeeping, and/or other business based financial processes.

FIG. 1 illustrates a system for formatting data from one software application source into a format compatible for importing into another software application.

As illustrated in FIG. 1, the system includes a client computing system 100. The client computing system 100 includes a display device or screen 10, a computing device 30 (having a processor, memory, and various input/output interfaces), and user interface 20 (such as a keyboard, mouse, or other type of pointing device).

The client computing system 100 may be connected to a server 150 through a local area network. The server 150 has a processor, memory, various input/output interfaces, etc.

The accounting application software may reside upon the client computing system 100 and/or the server 150. Also, the data file for the accounting application software may reside upon the client computing system 100 and/or the server 150.

Moreover, the client computing system 100 and the server 150 may be connected to an internet (cloud) server 170 through a wide area network 160.

In this situation, the accounting application software may reside upon the client computing system 100, the server 150, and/or the internet (cloud) server 170. Also, the data file for the accounting application software may reside upon the client computing system 100, the server 150, and/or the internet (cloud) server 170.

In formatting data from one accounting software application source into a format compatible for importing into another accounting software application, the user, using the client computing system 100, opens a spreadsheet application which has been modified with an extension that allows the user to pull data from an accounting software application. The user also opens the accounting software application from which data is to be pulled.

In this modified spreadsheet application, the display device 10 may display an activatable icon within the spreadsheet application's window that can be activated by the user interface 20.

FIG. 5 illustrates an example of the spreadsheet application having activatable icons 200. As illustrated in FIG. 5, the display device 10 displays a spreadsheet application's window 11 that has activatable icons 200, for activating extensions, and a spreadsheet work area 300.

It is noted that one of the activatable icons 200, upon activation, launches (initiates) the extension which enables transfer of data from the accounting software application to the spreadsheet work area 300.

More specifically, the initiated extension electronically connects the initiated extension with the launched accounting software application, through an application program interface of the launched accounting software application to create an electronic data channel between the initiated extension and the launched accounting software application.

As illustrated in FIG. 2, the user interface 20 enables transfer of data from the accounting software application to spreadsheet, at step S10. At step S20, the activated spreadsheet extension pulls data from the opened accounting software application.

It is noted that if the accounting software application needs user authentication, the extension enables the user to enter the appropriate authentication data (passwords, etc.) so that the data file associated with the accounting software application can be accessed.

At step S30, the pulled data is parsed into logical groups and the groups are written into a table in a database, as illustrated in FIG. 6. An example of a program that can facilitate the pulling, parsing, and writing of data, as discussed above, is Datablox™.

At step S40, each database table is analyzed and the data is reformatted or translated as needed. Unnecessary data can also be omitted in this step.

As illustrated in FIG. 7, the initial data may have an account type as “Bank.” However, when the database is analyzed at step S40, the process recognizes that the new accounting software application does not have “Bank” as an account type. Based upon this recognition, step S40 replaces (translates) “Bank” to “Cash” as the account type.

Furthermore, as illustrated in FIG. 7, the initial data may have an account type as “Loan.” However, when the database is analyzed at step S40, the process recognizes that the new accounting software application does not have “Loan” as an account type. Based upon this recognition, step S40 replaces (translates) “Loan” to “LT Liability” as the account type.

In addition, as illustrated in FIG. 7, the initial data may have an account type as “Other Expense.” However, when the database is analyzed at step S40, the process recognizes that the new accounting software application has an account type specifically directed to the account “Income tax expense.” Based upon this recognition, step S40 replaces (translates) “Other Expense” to “Taxes” as the account type.

It is noted that the opened accounting software application may use classes to categorize income and expenses for a single job or project. If the new accounting software application has a similar feature, but calls it projects, the class names may be translated to project names.

In analyzing the data pulled from the accounting software application, the process may utilize pre-determined maps (tables) that enable the mapping of the original account type of the original accounting software application to the new account type of the accounting software application.

For example, in the situation described above with respect to the account type “Bank,” the process may include a table entry that maps “Bank” to “Cash.”

It is noted that the extension may be transfer specific wherein the extension has pre-determined maps (tables) that enable the mapping of the original account type of the original accounting software application A to new accounting software application B.

It is also noted that the extension may have multiple pre-determined maps (tables), each associated with a specific transfer, such that the extension acquires from the user the identity of the original accounting software application and the identity of the new accounting software application and based upon the acquired identity information, the extension chooses the correct pre-determined maps (tables) to use in the analysis/translation routine.

It is further noted that dates (mm/yy/dd) and phone numbers (###-###-####) are often stored in different formats. Step S40 may reformat data in order for it to transfer successfully to the new accounting software application.

With respect to omitting data, if the opened accounting software application captures more data fields than the new accounting software application, the additional fields may be omitted at step S40.

In FIG. 3, at step S50, the new “data” is written from each table to its own worksheet in the spreadsheet. FIG. 8 illustrates an example of a vendor worksheet created from a vendor table having the new “data.”

After the new data is written into the spreadsheet, the user can review and/or edit the data before the data is transferred to the new accounting software application. It is also noted that the spreadsheet can be saved for future reference.

As noted above, in the modified spreadsheet application, the display device 10 may display an activatable icon within the spreadsheet application's window that can be activated by the user interface 20.

It is noted that one of the activatable icons 200 of FIG. 5, upon activation, launches the extension which enables transfer of data from the spreadsheet work area 300 to an accounting software application (step S60 of FIG. 3).

More specifically, the initiated extension electronically connects the initiated extension with the launched accounting software application, through an application program interface of the launched accounting software application to create an electronic data channel between the initiated extension and the launched accounting software application.

Upon activation of the extension for enabling transfer of data from the spreadsheet work area 300 to an accounting software application, at step S70, the data in spreadsheet is formatted into a format that is acceptable to the new accounting software application. For example, the data in spreadsheet is formatted into XML.

At step S70, the extension makes a request of the application program interface of the new accounting software application to transfer the formatted data to the new accounting software application.

At step S80, the client computing device may display a message from the new accounting software application indicating a successful transfer or a failed transfer.

FIG. 9 illustrates the transfer of the formatted data to the new accounting software application and a response indicating the state of the transfer.

In the description above, the extension provides a software bridge (user interface in the sense that a user uses the software platform as a bridge to interface between the two accounting software applications), which can readily accept the previous generation formatted files and effectively re-format the data for importing into the new generation accounting software application. The software bridge (user interface) may be ubiquitous in that the software bridge is readily available, easy to use, and has the ability to interface with numerous applications and platforms.

An example of a possible software platform to use in generating a software bridge is Microsoft™ spreadsheet software, Excel™, because Excel™ is readily available, easy to use, and has the ability to interface with numerous applications and platforms. It is also noted that in many cases, Excel™ has built-in wizards which provide ways of importing different types of file formats.

The software platform used to create the bridge (user interface) may be based upon a programming language that enables an extension of its capabilities.

For example, Microsoft™ provides a programming language Visual Basic for Applications that extends the capability of Excel™. By programming in Visual Basic for Applications, one can create an Excel™ Add-In for a user that provides custom features. The user can run the Visual Basic for Applications program by selecting menu options or buttons right from the Excel™ menu. The benefit of an Excel™ Add-In is the user can work within Excel™ and its familiar interface. The Add-In can act on data the user has entered and saved in Excel™. The user does not need to learn new software. Installing an Add-In takes just a few clicks.

It is noted that although Microsoft™ spreadsheet software, Excel™, has been discussed above, any software platform (application) that is readily available, easy to use, has the ability to interface with numerous applications and platforms, and is based upon a programming language that enables an extension of its capabilities can be utilized.

The Add-In feature of Excel™ may transfer (export) only journal entries into the accounting software application. A journal entry is one type of transaction that is commonly entered into an accounting software application. However, there are many other types of transactions and lists that a user might possibly want to transfer to the accounting software application.

For example, the Add-In feature of Excel™ may transfer (export) bills, invoices, purchase orders, checks, bank deposits, and/or estimates.

To summarize, the software bridge transfers data from directly within the software bridge to any accounting software application that offers the necessary interface(s). The data can represent any type of financial transaction that an accounting software user might want to transfer.

The software bridge “pushes” the data from within the software bridge to the new accounting software application rather than have the data “pulled” or “imported” to the new accounting software application because the “pull” approach is much more difficult for a user because the user must comply with the data format required by the new accounting software application, or the new accounting software application may not permit importing.

However, it is noted that the user may have to pull or import the data into the new accounting software application if the new accounting software application does not have an application program interface which enables the pushing of data from the software bridge to the new accounting software application.

The following description is an example of a software bridge, using Microsoft™ spreadsheet software, Excel™, as the platform and Intuit™ QuickBooks™ Online or QuickBooks™ Desktop, as the accounting software.

In the following description, it is assumed that the user has data in Excel™ to be transferred to QuickBooks™ Online or QuickBooks™ Desktop.

When executing an Add-In feature of Excel™ (created according to the described concepts), the user should have Excel™ open with the data to be transferred appearing in the active sheet.

By clicking an Add-In feature of Excel™; for example, XLtoQB; two buttons may be displayed for activation—either an IIF format button or a Columnar format button depending upon the initial format of the data that the user wishes to export to QuickBooks™ Online or QuickBooks™ Desktop.

For first-time users, clicking either button may begin a setup process that is discussed in more detail below.

For users having completed the setup, clicking one of the buttons button will execute a Visual Basic for Applications code. An example of such source code (Source Code 1) is provided below.

Upon clicking one of the buttons, a pop-up window is displayed.

The pop-up window may include a “Login to QuickBooks” button, which when it is clicked, another windows is displayed showing an Intuit™ prompt for the QuickBooks™ Online or QuickBooks™ Desktop username and password.

This window enables the user to sign into QuickBooks™ Online. If a user has multiple companies, a user may select any of the companies. The extension may display a window notifying the user that the extension has successfully connected to QuickBooks™ Online or QuickBooks™ Desktop if the sign in data was acceptable.

The following is an example of source code for an Excel™ Add-in which provides a software bridge for transferring data formatted in the Intuit™ Interchange Format (IIF) format to QuickBooks™ Online or QuickBooks™ Desktop.

Source Code 1 takes transaction data in Excel™ and transfers it to a desktop version of QuickBooks™ or an online version of Quickbooks™ using the QuickBooks™ Software Developer Kit.

For example, if a customer has a payroll transaction file to transfer to a desktop version of QuickBooks™ or an online version of Quickbooks™, the customer can utilize Source Code 1, as set forth below, to take payroll transaction data in Excel™ and transfer it to a desktop version of QuickBooks™ or an online version of Quickbooks™.

The following source code is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights to this source code.

Using a ubiquitous spreadsheet program as the tool to transfer data, as described above, simplifies the task of transferring data between accounting software applications.

In the explanation below, let the accounting software application, from which data is being taken, be named OLD and the target accounting software application be named NEW. The user opens the spreadsheet. It is noted that the data can be extracted from either desktop software or Online.

To initiate the process, a user activates an extension which launches software development kit (SDK) tools to extract data from OLD accounting software application. Authentication may be required by the OLD accounting software application to obtain permission to extract data.

Then the selected data is read and it is determined what data fields in OLD accounting software application can be successfully imported into NEW accounting software application. For example, if a fax number is in OLD accounting software application but not NEW accounting software application, that data field may be omitted.

The data from OLD accounting software application is reformatted to NEW accounting software application as needed. For example, if zip code in OLD accounting software application is nine digits and zip code in the NEW accounting software application is five digits, the last four digits are removed from OLD accounting software application data. The data is displayed in the correct columns as specified by the NEW accounting software application so the spreadsheet can be imported into NEW accounting software application.

The data is formatted to the NEW accounting software application's specifications. In other words, the user can now sign into NEW accounting software application and follow the instructions for importing a spreadsheet to have all their customers appear in the NEW accounting software application.

In another example, let the payroll service, from which the data that is being taken, be named PR and the target online accounting software be named OA.

Payroll service bureaus commonly create files in an IIF or columnar format. These files contain the data representing a journal entry for the payroll expenses for a given pay period. In this example, it is assumed the user has downloaded an IIF file from PR.

The user is instructed to open the IIF file with the spreadsheet.

Upon clicking on an extension in the spreadsheet application associated with IIF format, the data in the spreadsheet is evaluated to make sure it is in IIF format (the user may have modified it by mistake). Error messages will appear if the data does not comply with IIF format.

The data in the spreadsheet is checked for other error conditions. The amount column must sum to zero (debits=credits). Every row having an amount must have an Account. Error messages will appear if these criteria are not satisfied.

The data is written to an XML document that conforms to the OA's journal entry specification.

Using the OA's software development tools, a connection is made to the OA. Authentication may be required by the user.

The XML document is passed to the OA, and the journal entry can be seen by the user when the user logins to the OA.

Source Code 2 extracts transactions and lists from a desktop version of QuickBooks™ or an online version of Quickbooks™ writes the transactions and lists in an Excel™ workbook or worksheet.

For example, if a customer wants to stop using a desktop version of QuickBooks™ or an online version of Quickbooks™, the customer can utilize Source Code 2, as set forth below, to transfer the data from the desktop version of QuickBooks™ or the online version of Quickbooks™ to the new accounting software application.

The following example of source code (Source Code 2) is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights to this source code.

Source Code 3 extracts transactions and lists from a desktop version of QuickBooks™ writes the transactions and lists in an Excel™ workbook or worksheet, using Datablox™.

For example, if a customer wants to stop using a desktop version of QuickBooks™, the customer can utilize Source Code 3, as set forth below, to transfer the data from the desktop version of QuickBooks™ to the new accounting software application.

The following example of source code (Source Code 3) is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights to this source code.

Source Code 3 Public Sub qbi_GetData( ) ′CH 9/2/14 ′program needs ′reference′ to OfficeQ6 - but no include file Dim qbs As officeq6.Reader Dim nErr Dim rs As Recordset Dim a$ a = gini_SetRootDirs( )  ′--- qbs name is arbitrary, but makes code simple to edit  ′--- ole object - dim and create  ′--- OfficeQ6 is the Datablox product Set qbs = CreateObject(″OfficeQ6.Reader″)    ′--- read the QB company data and create a QQT file nErr = qbs.ReadFile(″″, ″qqtfile=″ & gsRootDirData & ″QBdata.qqt″) ′set the data source to be the qqt file gnDataSource = gnRemoteQQT ′populate the mdb from the qqt file nErr = qbi_ImportAllData(gsRootDirData & ″QBdata.qqt″, gsRootDirData & ″sprm_prod_2010.mdb″, ′′′′, True) nErr = qbs.Done( ) qbi_MDBtoExcel Set qbs = Nothing ′Note that this line is VERY IMPORTANT     ′It is what causes the program to disconnect from     ′the OfficeQ6 module and remove OfficeQ6 from memory End Sub Public Sub qbi_MDBtoExcel( ) ′added by CH ′data from mdb to excel Dim daoDB As DAO.Database Dim daoQueryDef  As DAO.QueryDef Dim daoRcd As DAO.Recordset Dim lastrow As Long Dim rowctr As Long Set daoDB = OpenDatabase(gsRootDirData & ″sprm_prod_2010.mdb″) ′company Set daoQueryDef = daoDB.QueryDefs(″qCompany″) Set daoRcd = daoQueryDef.OpenRecordset Sheets(″Company″).Cells.ClearContents Sheets(″Company″).Range(″A1″).CopyFromRecordset daoRcd ′accounts with balances Set daoQueryDef = daoDB.QueryDefs(″qFiscalYTDTrialBalance″) Set daoRcd = daoQueryDef.OpenRecordset Sheets(″Accounts″).Activate Sheets(″Accounts″).Cells.ClearContents Sheets(″Accounts″).Range(″A2″).CopyFromRecordset daoRcd Sheets(″Accounts″).Range(″A1″).Value = ″Account #″ Sheets(″Accounts″).Range(″B1″).Value = ″Account Name″ Sheets(″Accounts″).Range(″C1″).Value = ″Account Type″ Sheets(″Accounts″).Range(″D1″).Value = ″Description″ Sheets(″Accounts″).Range(″E1″).Value = ″Debit″ Sheets(″Accounts″).Range(″F1″).Value = ″Credit″ Sheets(″Accounts″).Columns(″E:G″).Style = ″Currency″ Sheets(″Accounts″).Cells.EntireColumn.AutoFit ′need to translate account types in QB to Kashoo. The TYPE value must be CAPS and have an underscore to replace a space for Kashoo   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″FixedAsset″, Replacement:=″FIXED_ASSET″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″AcctRec″, Replacement:=″ACCOUNTS_RECEIVABLE″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″AcctPay″, Replacement:=″ACCOUNTS_PAYABLE″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″OthCurrLiab″, Replacement:=″OTHER_CURRENT_LIABILITY″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″OthCurrAsset″, Replacement:=″OTHER_CURRENT_ASSET″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″COGS″, Replacement:=″COST_OF_GOODS_SOLD″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″CredCard″, Replacement:=″CREDIT_CARD″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″LongTermLiab″, Replacement:=″LONG_TERM_LIABILITY″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″OthAsset″, Replacement:=″OTHER_ASSET″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″OthIncome″, Replacement:=″INCOME″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″OthExpense″, Replacement:=″EXPENSE″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″Loan″, Replacement:=″LONG_TERM_LIABILITY″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″Bank″, Replacement:=″BANK″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″Expense″, Replacement:=″EXPENSE″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″Equity″, Replacement:=″EQUITY″   Sheets(″Accounts″).Columns(″C:C″).Replace What:=″Income″, Replacement:=″INCOME″ ′find Retained Earnings and change its type. Can't change its type to RE cause Kashoo already has 1 account type RE ′and does not permit a 2nd account with type RE ′lastrow = Sheets(″Accounts″).Range(″A″ & Rows.Count).End(xlUp).Row ′For rowctr = 2 To lastrow ′ If Sheets(″Accounts″).Cells(rowctr, 2).Value = ″Retained Earnings″ Then ′  Sheets(″Accounts″).Cells(rowctr, 3).Value = ″RETAINED_EARNINGS″ ′ End If ′Next ′customers Sheets(″Customers″).Cells.ClearContents Set daoQueryDef = daoDB.QueryDefs(″qCustomers″) Set daoRcd = daoQueryDef.OpenRecordset Sheets(″Customers″).Range(″A2″).CopyFromRecordset daoRcd Sheets(″Customers″).Range(″A1″).Value = ″Company Name″ Sheets(″Customers″).Range(″B1″).Value = ″Email″ Sheets(″Customers″).Range(″C1″).Value = ″First Name″ Sheets(″Customers″).Range(″D1″).Value = ″Last Name″ Sheets(″Customers″).Range(″E1″).Value = ″Street Address″ Sheets(″Customers″).Range(″F1″).Value = ″Street Address 2″ Sheets(″Customers″).Range(″G1″).Value = ″City″ Sheets(″Customers″).Range(″H1″).Value = ″State/Province″ Sheets(″Customers″).Range(″I1″).Value = ″Country″ Sheets(″Customers″).Range(″J1″).Value = ″Zip/Postal Code″ Sheets(″Customers″).Range(″K1″).Value = ″Phone″ Sheets(″Customers″).Range(″L1″).Value = ″Fax″ Sheets(″Customers″).Range(″M1″).Value = ″Mobile″ Sheets(″Customers″).Range(″N1″).Value = ″Toll-free″ Sheets(″Customers″).Range(″O1″).Value = ″Ship To Name″ Sheets(″Customers″).Range(″P1″).Value = ″Ship To Street″ Sheets(″Customers″).Range(″Q1″).Value = ″Ship to Street2″ Sheets(″Customers″).Range(″R1″).Value = ″Ship to city″ Sheets(″Customers″).Range(″S1″).Value = ″Ship to state or province″ Sheets(″Customers″).Range(″T1″).Value = ″Ship to country″ Sheets(″Customers″).Range(″U1″).Value = ″Ship to notes″ Sheets(″Customers″).Cells.EntireColumn.AutoFit ′vendors Sheets(″Vendors″).Cells.ClearContents Set daoQueryDef = daoDB.QueryDefs(″qVendors″) Set daoRcd = daoQueryDef.OpenRecordset Sheets(″Vendors″).Range(″A2″).CopyFromRecordset daoRcd Sheets(″Vendors″).Range(″A1″).Value = ″Company Name″ Sheets(″Vendors″).Range(″B1″).Value = ″Email″ Sheets(″Vendors″).Range(″C1″).Value = ″First Name″ Sheets(″Vendors″).Range(″D1″).Value = ″Last Name″ Sheets(″Vendors″).Range(″E1″).Value = ″Street Address″ Sheets(″Vendors″).Range(″F1″).Value = ″Street Address 2″ Sheets(″Vendors″).Range(″G1″).Value = ″City″ Sheets(″Vendors″).Range(″H1″).Value = ″State/Province″ Sheets(″Vendors″).Range(″I1″).Value = ″Country″ Sheets(″Vendors″).Range(″J1″).Value = ″Zip/Postal Code″ Sheets(″Vendors″).Range(″K1″).Value = ″Phone″ Sheets(″Vendors″).Range(″L1″).Value = ″Fax″ Sheets(″Vendors″).Range(″M1″).Value = ″Mobile″ Sheets(″Vendors″).Range(″N1″).Value = ″Toll-free″ Sheets(″Vendors″).Cells.EntireColumn.AutoFit ′transactions Sheets(″Transactions″).Cells.ClearContents Set daoQueryDef = daoDB.QueryDefs(″qTrans″) Set daoRcd = daoQueryDef.OpenRecordset Sheets(″Transactions″).Range(″A1″).CopyFromRecordset daoRcd Sheets(″Transactions″).Columns(″F:F″).Style = ″Currency″ Sheets(″Transactions″).Cells.EntireColumn.AutoFit Sheets(″Accounts″).Range(″A1″).Select End Sub Public Sub callback(control As IRibbonControl)  Select Case control.Tag  Case ″fromQB″: qbi_GetData  Case ″toPAO″: getaccountids  End Select End Sub

Source Code 4 transfers transactions and lists in Excel™ to the new accounting application software using the application program interface of the new accounting application software.

For example, if a customer wants to stop using a desktop version of QuickBooks™, the customer can utilize Source Code 4, as set forth below, to transfer the data from Excel™ to the new accounting software application.

The following example of source code (Source Code 4) is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights to this source code.

Source Code 4 Public Sub connKashoo( ) ′adds an account from the active sheet to Kashoo. Duplicate account names are not added and return an error. ′also duplicate account numbers are not added ′successfully adds accounts to PAO 9/15/14 Dim strToken As String Dim busID As String Dim XMLHttp As New MSXML2.XMLHttp Dim strData As String Dim aNumber As String Dim aName As String Dim aType As String Dim aDesc As String Dim xmlAcct As String Dim xmlAddAcct As String Dim dt As String Dim c As String Dim lastrow As Long Dim rowctr As Long Dim wksSheet As Excel.Worksheet Dim sheetname As String Application.Cursor = xlWait sheetname = ″Accounts″ Set wksSheet = Application.ActiveSheet lastrow = Range(″A″ & Rows.Count).End(xlUp).Row Select Case sheetname Case ″Accounts″ dt = Chr(34) & Format(Date, ″yyyy-mm-dd″) & Chr(34) For rowctr = 2 To lastrow  aNumber = Chr(34) & wksSheet.Cells(rowctr, 1).Value & Chr(34)  aName = Chr(34) & wksSheet.Cells(rowctr, 2).Value & Chr(34)  aType = Chr(34) & wksSheet.Cells(rowctr, 3).Value & Chr(34)  aDesc = Chr(34) & wksSheet.Cells(rowctr, 4).Value & Chr(34)  xmlAcct = ″<account description =″ & aDesc & ″ name = ″ & aName & ″ number = ″ & aNumber & ″ openDate = ″ & dt & ″ type = ″ & aType & ”/>″  xmlAddAcct = ″<?xml version=″″1.0″″ encoding=″″UTF-8″″ standalone=″″yes″″?>″ & xmlAcct  XMLHttp.Open ″POST″, ″https://api.paychexaccounting.com/api/businesses/23468118456/accounts″, False  XMLHttp.send xmlAddAcct  strData = strData & XMLHttp.responseText  xmlAcct = ″″  xmlAddAcct = ″″ Next rowctr Case ″Customers″ Case ″Vendors″ Case ″fiscalyeartotdatetrialbalance″ End Select ′successsfully gets a token by prompting user for credentials ′XMLHttp.Open ″POST″, ″https://api.kashoo.com/api/authTokens″, False, ″″, ″″ ′XMLHttp.send ′strToken = XMLHttp.responseText ′get business ids connected to user. will fail if one or more businesses are expired XMLHttp.Open ″GET″, ″https://api.paychexaccounting.com/api/users/me/businesses″, False XMLHttp.setRequestHeader ″Authorization″, ″AuthSub token=″ & strToken XMLHttp.send busID = XMLHttp.responseText ′successful 9.15.14 ′Dim strData As String ′XMLHttp.Open ″GET″, ″https://api.paychexaccounting.com/api/users/me″, False ′XMLHttp.setRequestHeader ″Authorization″, ″AuthSub token=″ & strToken ′XMLHttp.send ′strData = XMLHttp.responseText Application.Cursor = xlDefault End Sub Public Sub postje(id As Double) ′purpose is to post journal entries to PAO. I was unable to determine the correct XML form to place multiple ′journal entries into one XML document. As a result I post and send each journal entry. This may be OK since I get a ′response for each journal entry as to its success or failure. Dim strResp As String Dim XMLHttp As New MSXML2.XMLHttp Dim wksSheet As Excel.Worksheet Dim rowctr As Long Dim lastrow As Long Dim trnDate As String Dim trnNum As Long Dim trnType As String Dim trnAmt As String Dim trnAmount As Long Dim trnAccount As String Dim xmlJE As String Set wksSheet = Application.ActiveSheet lastrow = Range(″A″ & Rows.Count).End(xlUp).Row ′loop thru all rows in active sheet For rowctr = 1 To lastrow  xmlJE = ″<?xml version=″″l.0″″ encoding=″″UTF-8″″ standalone=″″yes″″?>″  ′set values for header of journal entry  trnNum = wksSheet.Cells(rowctr, 1).Value  trnDate = Chr(34) & Format(wksSheet.Cells(rowctr, 2).Value, ″yyyy-mm-dd″) & Chr(34)  trnType = Chr(34) & wksSheet.Cells(rowctr, 3).Value & Chr(34)  xmlJE = xmlJE & ″<manualAdjustmentRecord memo=″″QuickBooks import″″ currency=″″USD″″ date= ″ & trnDate & ″ number = ″ & trnType & ″> <adjustments>″   ′loop thru each row having same transaction ID. These rows create the journal entry.   Do While trnNum = wksSheet.Cells(rowctr, 1).Value    trnAccount = Chr(34) & wksSheet.Cells(rowctr, 7).Value & Chr(34)    trnAmount = Str$(−100 * wksSheet.Cells(rowctr, 6).Value)    trnAmt = Chr(34) & trnAmount & Chr(34)    xmlJE = xmlJE & ″<adjustment account= ″ & trnAccount & ″ amount= ″ & trnAmt & ″ currency=″″USD″″/>″    rowctr = rowctr + 1   Loop   xmlJE = xmlJE & ″</adjustments> </manualAdjustmentRecord>″   rowctr = rowctr − 1   XMLHttp.Open ″POST″, ″https://api.paychexaccounting.com/api/businesses/″ & id & ″/records/adjustments″, False   XMLHttp.send xmlJE   strResp = strResp & XMLHttp.responseText   xmlJE = ″″ Next rowctr End Sub

In summary, a method and system automatically convert formatted data from one software application source into a format compatible for importing into another software application, using a third software application by launching, through a user's interaction with a user interface associated with the computer, a spreadsheet application; launching, through a user's interaction with a user interface associated with the computer, a first accounting software application; initiating, through a user's interaction with the user interface associated with the computer, a first extension of the launched spreadsheet application; electronically connecting the initiated first extension with the launched first accounting software application, through an application program interface of the launched first accounting software application, to create a first electronic data channel between the initiated first extension and the launched first accounting software application; electronically pulling, by the initiated first extension, accounting data from the launched first accounting software application through the first electronic data channel to the initiated first extension; electronically converting, by the initiated first extension, the pulled data into a format compatible with a second accounting software application; electronically writing, by the initiated first extension, the converted data into a workbook created by the launched spreadsheet application; launching, through a user's interaction with the user interface associated with the computer, a second accounting software application; initiating, through a user's interaction with the user interface associated with the computer, a second extension of the launched spreadsheet application; electronically connecting the initiated second extension with the launched second accounting software application, through an application program interface of the launched second accounting software application to create a second electronic data channel between the initiated second extension and the launched second accounting software application; electronically converting, by the initiated second extension, the converted data in the workbook to a format compatible for importing into the launched second accounting software application; and electronically pushing the format compatible data into the launched second accounting software application.

The electronic conversion by the initiated second extension may convert the converted data in the workbook to a XML format. The electronic conversion by the initiated first extension may convert the pulled data by using pre-determined tables which map data fields of the launched first accounting software application to data fields of the launched second accounting software application. The converted data in the workbook may be edited by a user before the second extension of the launched spreadsheet application is initiated through a user's interaction with the user interface associated with the computer.

The launched spreadsheet application may reside on the computer and the accounting data from the launched first accounting software application may reside on the computer.

The launched spreadsheet application may reside on the computer and the accounting data from the launched first accounting software application may reside on a second computer communicatively connected to the computer through a local area network.

The launched spreadsheet application may reside on the computer and the accounting data from the launched first accounting software application may reside on a second computer communicatively connected to the computer through a wide area network.

The launched spreadsheet application may reside on the computer and the accounting data for the launched second accounting software application may reside on the computer.

The launched spreadsheet application may reside on the computer and the accounting data for the launched second accounting software application may reside on a second computer communicatively connected to the computer through a local area network.

The launched spreadsheet application may reside on the computer and the accounting data for the launched second accounting software application may reside on a second computer communicatively connected to the computer through a wide area network.

It is noted that the various embodiments may be carried out by a processor executing software corresponding to the source code described herein or the various embodiments may be carried out by firmware executing processes corresponding to the source code described herein.

It is further noted that processes described herein may be carried out in a single computer, over a local area network, or over a wide area network (internet or cloud).

It will be appreciated that variations of the above-disclosed embodiments and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. Also, various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the description above. 

What is claimed is:
 1. A method, using a computer, for automatically converting formatted data from one software application source into a format compatible for importing into another software application, using a third software application, comprising: (a) launching, through a user-initiated first interaction with a user interface associated with the computer, a first software application; (b) importing, through a user-initiated third interaction with the user interface associated with the computer, an electronic file of data associated with a second software application into the launched first software application; (c) electronically translating, by the launched first software application, the imported electronic file of data associated with the second software application into new data which is import format compatible for importing into an accounting software application; (d) launching an application programing interface associated with the accounting software application; (e) electronically connecting with the launched accounting software application, through the launched application program interface, to create an electronic data channel between the launched first software application and the accounting software application; and (f) electronically pushing the import format compatible new data into the accounting software application.
 2. The method as claimed in claim 1, wherein the electronic conversion by the initiated second extension formats the new data in the workbook to a XML format.
 3. The method as claimed in claim 1, wherein the electronic translation by the initiated first extension translates the pulled data by using pre-determined tables which map data fields of the launched first accounting software application to data fields of the launched second accounting software application.
 4. The method as claimed in claim 1, wherein the new data in the workbook is edited by a user before the second extension of the launched spreadsheet application is initiated through the fifth user-initiated interaction with the user interface associated with the computer.
 5. The method as claimed in claim 1, wherein the launched spreadsheet application resides on the computer and the accounting data from the launched first accounting software application resides on the computer.
 6. The method as claimed in claim 1, wherein the launched spreadsheet application resides on the computer and the accounting data from the launched first accounting software application resides on a second computer communicatively connected to the computer through a local area network.
 7. The method as claimed in claim 1, wherein the launched spreadsheet application resides on the computer and the accounting data from the launched first accounting software application resides on a second computer communicatively connected to the computer through a wide area network.
 8. The method as claimed in claim 1, wherein the launched spreadsheet application resides on the computer and the accounting data for the launched second accounting software application will reside on the computer.
 9. The method as claimed in claim 1, wherein the launched spreadsheet application resides on the computer and the accounting data for the launched second accounting software application will reside on a second computer communicatively connected to the computer through a local area network.
 10. The method as claimed in claim 1, wherein the launched spreadsheet application resides on the computer and the accounting data for the launched second accounting software application will reside on a second computer communicatively connected to the computer through a wide area network.
 11. A system for automatically converting formatted data from one software application source into a format compatible for importing into another software application, using a third software application, comprising: a computer including a processor, memory, and a user interface; said processor launching, through a user-initiated first interaction with a user interface associated with the computer, a first software application; said processor importing, through a user-initiated third interaction with the user interface associated with the computer, an electronic file of data associated with a second software application into the launched first software application; said processor electronically translating, by the launched first software application, the imported electronic file of data associated with the second software application into new data which is import format compatible for importing into an accounting software application; said processor launching an application programing interface associated with the accounting software application; said processor electronically connecting with the launched accounting software application, through the launched application program interface, to create an electronic data channel between the launched first software application and the accounting software application; and said processor electronically pushing the import format compatible new data into the accounting software application.
 12. The system as claimed in claim 11, wherein the electronic conversion by the initiated second extension formats the new data in the workbook to a XML format.
 13. The system as claimed in claim 11, wherein the electronic translation by the initiated first extension translates the pulled data by using pre-determined tables which map data fields of the launched first accounting software application to data fields of the launched second accounting software application.
 14. The system as claimed in claim 11, wherein the new data in the workbook is edited by a user before the second extension of the launched spreadsheet application is initiated through the fifth user-initiated interaction with the user interface associated with the computer.
 15. The system as claimed in claim 11, wherein the launched spreadsheet application resides on said computer and the accounting data from the launched first accounting software application resides on said computer.
 16. The system as claimed in claim 11, wherein the launched spreadsheet application resides on said computer and the accounting data from the launched first accounting software application resides on a second computer communicatively connected to said computer through a local area network.
 17. The system as claimed in claim 11, wherein the launched spreadsheet application resides on said computer and the accounting data from the launched first accounting software application resides on a second computer communicatively connected to said computer through a wide area network.
 18. The system as claimed in claim 11, wherein the launched spreadsheet application resides on said computer and the accounting data for the launched second accounting software application will reside on said computer.
 19. The system as claimed in claim 11, wherein the launched spreadsheet application resides on said computer and the accounting data for the launched second accounting software application will reside on a second computer communicatively connected to said computer through a local area network.
 20. The system as claimed in claim 11, wherein the launched spreadsheet application resides on said computer and the accounting data for the launched second accounting software application will reside on a second computer communicatively connected to said computer through a wide area network. 